An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

App name: Bromure Client App id: 6793724385 Submission id: 33c98717-eb8d-4b2d-867e-0cc0bf2ef89d My app has been suck in the state of "in review" since 7/31. The credentials provided to test the app have never been used by the Apple team. I emailed support -- never received any answer. Does anyone have any idea on what could be happening? I initially submitted the app on 7/27. How much longer should I expect to wait?

It has been a week since we submitted our app update, and the app is still in Pending Review. We previously contacted Apple Support regarding this issue and received a case ID via email. However, we have not received any response or update on the status of our case. We also could not find any place to track the case using the case ID that was provided.

Hi Apple team, App: DEADGRID Version: 2.0.1 App Apple ID: 6790152649 I'm reaching out in the hope that someone from the App Review team can take a look at my submission or advise whether there's an issue with it. My app has been in "Waiting for Review" for over a week and has not yet entered the "In Review" stage. I understand review times can vary, but this is significantly longer than what I've experienced previously. I've done my best to follow all App Store Review Guidelines and have provided complete review notes. As far as I'm aware, there isn't anything unusual about this submission that would explain the delay. Unfortunately, this update contains a fix for an issue currently affecting my users. While it's waiting to be reviewed, I'm seeing a decline in daily active users and user retention because I'm unable to release the fix. If someone from Apple is able to check whether my submission is simply waiting in the normal queue or if there's another issue preventing it from being reviewed, I would be very grateful. I'd also be interested to hear from other developers: Have you experienced similar review delays recently? Is there anything that can help move a submission forward when it's been waiting for this long? Are there any common reasons for an app to remain in "Waiting for Review" for more than a week? I appreciate the work of the App Review team and understand the volume of submissions you process every day. I'm mainly hoping someone can verify that my submission hasn't become stuck or overlooked. Thank you for your time. Afonso Quinaz

My app was rejected July 16 under Guideline 2.1 (Information Needed) with four questions about the Clinical Health Records API. I replied in full the same day in the Resolution Center, and followed up in that thread on July 22. It has now been 12 days with no response from App Review. I have also contacted Developer Support (case 102942988807), which replied twice but could not provide status on the submission. I have not clicked Resubmit, since Apple's message asked me to reply, and I understand resubmitting closes the correspondence thread. Is there anything further I should be doing, or is a reply alone sufficient to return the submission to the review queue? Submission ID: bc855e56-3ef8-482d-96b0-4380d3fc4a68

Hello, My app Air Finder - My Device Tracker (Apple ID: 1490211589) seems to be stuck in the App Review process and I'd like to check if something might be wrong with my submission. Timeline: Submission for review: Jul 30, 2026 Current status: Waiting for Review Waiting time: 7 days as of Aug 6, 2026 My app reviews are typically approved within 1-2 business days, so I suppose this delay seems to be unusual. Please help review this submission as soon as possible! I have a timeline for publishing app version that cannot be delayed for this long. Any guidance would be very appreciated. Thank you in advance!

Hi, I submitted Mendo (iOS, version 0.1.0) for App Review on Thursday at 12:39 AM. It’s still Waiting for Review. I had earlier submissions of the same version that I removed myself because I needed to make updates. The current submission is the one I want reviewed. I understood App Review usually takes around 48 hours, but it’s been longer than that for me. Is this delay normal right now, or is there something I should check on my end? Otherwise can I at least get some sort of acknowledgement of some sort to the tickets I've created: - case ID is 20000125052237 case ID is 20000126237735 Thanks.

I am reaching out because my app has been stuck in “Waiting for Review” since July 27, and despite every effort to obtain an update, I have received no response. Over the past several days, I have: Contacted Apple Developer Support by phone multiple times and no response Sent multiple follow-up emails requesting a status update. Unfortunately, I still have not received any update. This delay is causing significant disruption to our launch. We have already committed resources to marketing campaigns, promotional materials, social media announcements, and launch planning based on the expectation that the app would be reviewed within a reasonable timeframe. If there is anything preventing the review from moving forward, or if additional information is needed from my side, I am ready to respond immediately. Developer: thespinu@hotmail

Hello to all1 I have an app currently published on Android and immediately pivoted to publishing the app on Apple, and was pretty excited about the response time from support when signing up for an account. I build the app using RN, so the move to Apple was fairly simple. Works great on my phone. That said, I'm still waiting for Apple to review my app. It's only been 3 days, but Apple says 90% of apps take 48 hours. Is that accurate? I submitted a ticket as well and never received a response.

Hello everyone. I’m trying to submit my first auto-renewable subscription with my iOS app, but can’t associate the subscription with my app version in App Store Connect. Setup: app version 1.0.7 with build attached, subscription group “Premium” with weekly, monthly, yearly. All metadata complete; paid apps agreement active, bank details set, admin access confirmed. Problem: “In-App Purchases and Subscriptions” section is missing on my app version page, so I can’t attach my subscription. Draft error says, “Unable to submit for review. Add an app version for the selected platform.” The draft only lists my weekly plan, not the app version. Questions: why might that section be missing? Are there prerequisites? Has anyone seen this? Any guidance or suggestions would be greatly appreciated.

Hi all, I submitted an update for my app (VowFolio, bundle ID com.helgemeisal.vowfolio) for review almost a week ago, and it's still sitting in "Waiting for Review." It hasn't even moved to "In Review" yet. This is a minor update, just bug fixes and small improvements, so I wasn't expecting anything close to this long a wait. Typical turnaround for me has been 24 to 48 hours, so this is a significant outlier. No rejection, no request for more information, no message in Resolution Center. It's just sitting there. A few questions for the community: Has anyone else noticed longer queue times recently? Is there a recommended way to check on status beyond just waiting, or to nudge the review team without risking a rejection? At what point does it make sense to reach out to Apple Developer Support directly? Any insight from others who've hit similar delays would be appreciated. Thanks!

Hi, Is there a reason why app reviews are taking longer than usual to be completed it has been over a week now since I submitted my app for review.

Our app sells two auto-renewable subscriptions. Product loading succeeds and returns both products with correct localized prices, but every purchase attempt fails roughly one second later with "Item Unavailable". No purchase sheet is ever presented to the user. The app has not yet passed its first App Review. It was rejected under Guideline 2.1(b) because the reviewer encountered this same error on their device. MY QUESTION Under what conditions does StoreKit reject a purchase with "Item Unavailable" for a product that has just been returned successfully, with a valid localized price, by a product request? Is an auto-renewable subscription transactable in the sandbox environment for an app that has never had a binary approved by App Review? Question 2 is the one I most need answered. App Review's rejection states that In-App Purchase products "do not need prior approval to function in review", but neither we nor the reviewer can transact them. DIAGNOSTIC LOG Captured on-device during a failing session: 01:08:56 fetchProducts [com.aurascanner.app.pro.weekly, com.aurascanner.app.pro.annual] 01:08:56 fetchProducts -> 2 product(s): com.aurascanner.app.pro.annual=$39.99; com.aurascanner.app.pro.weekly=$6.99 01:08:56 requestPurchase sku=com.aurascanner.app.pro.weekly 01:08:57 purchaseError: code=purchase-error msg=Item Unavailable 01:08:57 error code=purchase-error, storefront=USA 01:09:05 fetchProducts -> 2 product(s), same prices returned again 01:09:05 requestPurchase sku=com.aurascanner.app.pro.annual 01:09:06 requestPurchase threw: Item Unavailable 01:09:06 error code=purchase-error, storefront=USA An introductory-offer eligibility check earlier in the session also succeeded, using the subscription group ID read from the loaded product. So product metadata, including the subscription group, resolves correctly. CONDITIONS Fails identically for both products, on every attempt. Reproduces in TestFlight on our own devices and Apple IDs. Also failed during App Review on iPad Air 11-inch (M3), iPadOS 26.5.2. Storefront reports as USA in every case. Real devices only. Not reproduced on Simulator. ALREADY VERIFIED Paid Applications Agreement: Active, banking and tax information complete. In-App Purchase capability: enabled on the App ID at Certificates, Identifiers & Profiles. Bundle identifier com.aurascanner.app matches the App Store Connect record. Both subscriptions: complete metadata, review screenshots uploaded, USD pricing set, United States availability. Both subscriptions and the subscription group are attached to the current submission, status "Ready for Review". Subscription group has a localized display name. Build distributed via TestFlight, which routes purchases to sandbox automatically. IMPLEMENTATION The app is React Native and uses a wrapper library over StoreKit 2, but the error text originates from StoreKit rather than the wrapper, and the call order follows the documented pattern: Initialize the StoreKit connection. Load products. This succeeds and returns both products. Register transaction update and error listeners. Request the purchase. This is where it fails. Purchases are verified server-side using Apple's App Store Server Library, and the transaction is finished only after verification succeeds. I am not asking anyone to debug the wrapper. My question is about StoreKit and App Store behaviour: what causes the store to quote a product and then decline to sell it? Any pointers appreciated. I can supply screenshots or the full log.

Hello Apple Developer Support, Our first App Store submission has been in "Waiting for Review" since July 30, 2026, and it has not yet entered the review process. App information App: PigHub Marketplace Apple ID: 6791982179 Version: 1.0.8 (Build 5) We have also opened a Developer Support case regarding this issue, but we have not yet received a response after several days. Support Case ID: 20000126933752 This delay has unfortunately caused us to miss our planned public launch, so we would greatly appreciate your assistance in verifying that our submission is progressing normally. We understand that review times can vary. However, after several days, our submission remains in Waiting for Review without moving to In Review. We have also noticed that several other developers are currently reporting similar delays on the Apple Developer Forums. Could you please confirm that our submission is correctly queued and not affected by any App Store Connect or App Review issue? If there is any additional information or action required from our side, we would be happy to provide it immediately. Thank you very much for your time and assistance.

apple claimed that the game will be after review in 48 hours, i'm waiting for 2 weeks and i feel like i got scammed by apple. this is crazy! no response to emails and opening tickets. no one to talk to! Date Submitted Jul 25, 2026 at 1:17 AM Submission ID a5bd957b-7cd8-409f-a9d1-e3c5652952be

Our game Sand Sort 3D was rejected under Guideline 4.3(a) for binary similarity with our other titles. Three problems: False rejection: it's an original game: its simulation code, shaders and levels exist in no other app. The flagged overlap is shared infrastructure, not content: Unity engine resources, brand fonts, licensed Asset Store packs, and our own internal SDK (sign-in, IAP, ads, cloud save, analytics, consent) that we reuse across our catalogue. On our own audit, engine and font data are the bulk of the overlap; content we designed is ~4%, limited to a coin icon and a settings toggle. No gameplay code, levels, art or design is shared with anything we publish. Insufficient directions: the notice cited 4.3(a) without naming a single element of the app, so we have no actionable way to comply. If it's rejected again, please identify the specific content at issue. Long review times: this rejection has held the release 15 days, and review on this app and our other titles is averaging 10+ days — unusually long. A component-by-component breakdown is attached as appeal; the game is already live on Google Play.

Hi, Our macOS app has been in Waiting for Review since Jul 24, 2026 with no status change. Platform: macOS Version: 1.0 (1) App Apple ID: 6794145764 Submission ID: 5d04a433-b67d-4801-8578-b1ccc3f22d34 Support case: 20000126982226 We also requested an expedited review and contacted support more than once; no reply so far. Our earlier iOS submission was reviewed within a few days. This macOS one hasn’t moved at all. Is anyone else seeing long macOS “Waiting for Review” times right now? Any advice on getting this unstuck, or can someone from App Review take a look? Thanks.

Hello Apple Support Team, I'd like to kindly request an update regarding our latest app submission, which has remained in Waiting for Review since July 30, 2026. As of today (August 5), it has been 6 days without entering the review process. App Information App Name: Dora - AI Video Generator 2 Apple ID: 1604739131 Item for Review: App Version This submission is a major UI/UX revamp that significantly improves the overall user experience. After a long period of maintaining and iterating on the product, we redesigned many core user flows to provide a much more seamless and intuitive experience for our users. Our app continues to receive a large number of daily active users, so having this build remain in Waiting for Review is preventing them from accessing these important improvements and new experiences. The prolonged delay is having a meaningful impact on our users as well as our product rollout. We completely understand that review times can vary, but given the circumstances, we would greatly appreciate it if the review could be prioritized or expedited whenever possible. Thank you very much for your time and support. We truly appreciate the work of the App Review team and look forward to your response. Kind regards,

[Foxify] Version 1.1.1 (13) Review Hello Apple Support Team, My app's new app version and In-App Purchase appear to be stuck in the review process, and I'd like to check whether there might be an issue with the submission. App Information App Name: Foxify AI - Make Your Own Song. Apple ID: 6761515837. Items for Review: New App Version and New Consumable In-App Purchase. Timeline Submitted: July 21, 2026, at 10:57 AM. As of today (July 27), both the app version and the In-App Purchase have remained in "Waiting for Review" for 7 days. Context We submitted a new app version after addressing the issues raised during the previous review. At the same time, we submitted our first new consumable In-App Purchase, which requires the binary build to test the purchase flow, which has also been stuck for a while and has been rejected a few times due to build rejections and the item itself without a clear reason, so the Apple Review team could test the updated purchase flow together with the new IAP. Normally, both our app updates and In-App Purchases are reviewed within 1–2 days, so this delay seems unusual. Please kindly review the submission. Any guidance or assistance would be greatly appreciated. Thank you for your time and support.

Hi, Ive added a new version of my app for review a week ago. Jul 29, 2026 at 10:02 PM. Can someone explain what is taking so long? My new versions before this only took 24-48 hours. Its really difficult to fix and update bug fixes when it takes to long to get approved. Hoping this issue will be resolved quickly

Hello Apple, Our app "HealiFii Wellness" (Bundle ID: com.healifi.app) was submitted for review on July 29, 2026, and it has remained in "Waiting for Review" status for over one week. We have verified the following: No pending agreements or business requirements. No messages in the Resolution Center. The required DSA declaration has been completed. The app is available for distribution. The build has been successfully validated. Could someone please check if there is any issue with our submission or confirm whether it is still in the review queue? Please let us know if any additional information is required from our side. Thank you.